Improve Ava voice, continuity, and message clarity - #30
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
Customers were waiting too long for audible responses, Ava could hear and interrupt herself, the browser discarded visible history after hosted sign-in, and purchase requests could receive an unverified success claim. Outgoing messages also lacked a strong, consistent sender distinction.
Impact
Voice replies begin playing progressively, the microphone is protected during assistant playback, authenticated returns keep the existing conversation visible, and Ava states truthfully that nothing was ordered or charged. Customer messages now use a blue-on-pale-blue treatment with measured WCAG AA contrast.
Validation
npm run check